home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d20
/
xlist213.arc
/
X_LIST.DOC
< prev
next >
Wrap
Text File
|
1991-04-23
|
135KB
|
4,292 lines
X_List Version 2.13
===================
An eXtended AVAIL file generator
For Opus v1.03 and Opus v1.1x compatible BBS systems.
For Maximus CBCS 1.02 compatible BBS systems.
For QuickBBS 2.64 compatible BBS systems.
For RemoteAccess 0.04 compatible BBS systems.
X_List was Original written by Kristian Ottosen, 2:231/34.13
X_List Versions above 2.05 updated by Per Holm, 2:230/22
X_List documentation original by Stig Jacobsen, 2:231/16
X_List documentation Modified by Per Holm, 2:230/22
with help from George Cordner, 2:25/200,
And Louise Thomasen, 2:231/34.22.
Adjust program by Stig Jacobsen, The Ideal Copy, 2:231/16
Adjust versions above 2.11 updated by Per Holm, 2:230/22
MakeXDir & X_VanVab programs by Per Holm, Asgaard BBS, 2:230/22
Based on Original programs by Kristian Ottosen, 2:231/34.13
Comments & suggestions: to
--------------------------
Per Holm
Asgaard BBS
FidoNet: 2:230/22
SigNet: 27:1345/100
EggNet: 97:9451/4
24 hour crashmail accepted at:
++45-86-119043
or
perholm@daimi.AAU.DK
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
CONTENTS
LICENSE . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . 10
REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . 11
RUNNING X_LIST . . . . . . . . . . . . . . . . . . . . . . . 12
CONTROLFILE - GENERAL . . . . . . . . . . . . . . . . . . . . 13
License . . . . . . . . . . . . . . . . . . . . . . . . 13
PrmFile . . . . . . . . . . . . . . . . . . . . . . . . 13
SysOp . . . . . . . . . . . . . . . . . . . . . . . . . 13
SystemPath . . . . . . . . . . . . . . . . . . . . . . . 13
AreaFile . . . . . . . . . . . . . . . . . . . . . . . . 14
XListData . . . . . . . . . . . . . . . . . . . . . . . 14
XLogFile . . . . . . . . . . . . . . . . . . . . . . . . 14
LogLevel . . . . . . . . . . . . . . . . . . . . . . . . 15
FileMode . . . . . . . . . . . . . . . . . . . . . . . . 15
BBS . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Mailer . . . . . . . . . . . . . . . . . . . . . . . . . 16
BoardName . . . . . . . . . . . . . . . . . . . . . . . 16
Address . . . . . . . . . . . . . . . . . . . . . . . . 16
Zone . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Net . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Node . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Point . . . . . . . . . . . . . . . . . . . . . . . . . 17
Drives . . . . . . . . . . . . . . . . . . . . . . . . . 17
MaxDrive . . . . . . . . . . . . . . . . . . . . . . . . 17
Debug . . . . . . . . . . . . . . . . . . . . . . . . . 17
Hindustan . . . . . . . . . . . . . . . . . . . . . . . 17
CONTROLFILE - PUBLIC LIST . . . . . . . . . . . . . . . . . . 18
OutFile . . . . . . . . . . . . . . . . . . . . . . . . 18
NewsList . . . . . . . . . . . . . . . . . . . . . . . . 18
CommaFile . . . . . . . . . . . . . . . . . . . . . . . 18
CommaFormat . . . . . . . . . . . . . . . . . . . . . . 19
Index . . . . . . . . . . . . . . . . . . . . . . . . . 19
MaxFiles . . . . . . . . . . . . . . . . . . . . . . . . 19
Header . . . . . . . . . . . . . . . . . . . . . . . . . 20
Footer . . . . . . . . . . . . . . . . . . . . . . . . . 20
Level . . . . . . . . . . . . . . . . . . . . . . . . . 20
Skip <nn> . . . . . . . . . . . . . . . . . . . . . . . 21
Skip Barricaded . . . . . . . . . . . . . . . . . . . . 21
Skip Text . . . . . . . . . . . . . . . . . . . . . . . 21
Skip Missing . . . . . . . . . . . . . . . . . . . . . . 21
Show . . . . . . . . . . . . . . . . . . . . . . . . . . 21
First . . . . . . . . . . . . . . . . . . . . . . . . . 22
X_LIST 2.13 - PAGE 2
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
Last . . . . . . . . . . . . . . . . . . . . . . . . . . 22
MaxAreas . . . . . . . . . . . . . . . . . . . . . . . . 22
MarkLast . . . . . . . . . . . . . . . . . . . . . . . . 22
EuroDate . . . . . . . . . . . . . . . . . . . . . . . . 22
Lan-Ud . . . . . . . . . . . . . . . . . . . . . . . . . 22
Lan-Fa . . . . . . . . . . . . . . . . . . . . . . . . . 23
Lan-Fr . . . . . . . . . . . . . . . . . . . . . . . . . 23
Lan-Fp . . . . . . . . . . . . . . . . . . . . . . . . . 23
Lan-Mi . . . . . . . . . . . . . . . . . . . . . . . . . 23
Lan-Fl . . . . . . . . . . . . . . . . . . . . . . . . . 23
Lan-NF . . . . . . . . . . . . . . . . . . . . . . . . . 23
CONTROLFILE - AREA MAINTENANCE . . . . . . . . . . . . . . . 24
Rewrite . . . . . . . . . . . . . . . . . . . . . . . . 24
Adopt . . . . . . . . . . . . . . . . . . . . . . . . . 24
ReFlow . . . . . . . . . . . . . . . . . . . . . . . . . 25
RemMiss . . . . . . . . . . . . . . . . . . . . . . . . 25
Crap . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Secure . . . . . . . . . . . . . . . . . . . . . . . . . 25
ZapZero . . . . . . . . . . . . . . . . . . . . . . . . 26
DupeReport . . . . . . . . . . . . . . . . . . . . . . . 26
OrphanReport . . . . . . . . . . . . . . . . . . . . . . 26
KeepLatest . . . . . . . . . . . . . . . . . . . . . . . 27
Touch . . . . . . . . . . . . . . . . . . . . . . . . . 27
AdoptComment . . . . . . . . . . . . . . . . . . . . . . 27
Convert . . . . . . . . . . . . . . . . . . . . . . . . 27
CONTROLFILE - OKFILE GENERATION . . . . . . . . . . . . . . . 28
OkFile . . . . . . . . . . . . . . . . . . . . . . . . . 28
OkHeader . . . . . . . . . . . . . . . . . . . . . . . . 28
Password All . . . . . . . . . . . . . . . . . . . . . . 28
Password nn . . . . . . . . . . . . . . . . . . . . . . 28
Magic . . . . . . . . . . . . . . . . . . . . . . . . . 29
CONTROLFILE - LOGFILE ANALYSIS . . . . . . . . . . . . . . . 30
LogFile . . . . . . . . . . . . . . . . . . . . . . . . 30
Upload . . . . . . . . . . . . . . . . . . . . . . . . . 30
Download . . . . . . . . . . . . . . . . . . . . . . . . 30
DailyReport . . . . . . . . . . . . . . . . . . . . . . 30
SessionReport . . . . . . . . . . . . . . . . . . . . . 31
CoSysOp . . . . . . . . . . . . . . . . . . . . . . . . 32
Include . . . . . . . . . . . . . . . . . . . . . . . . 32
UserAdjust . . . . . . . . . . . . . . . . . . . . . . . 33
FreeFile . . . . . . . . . . . . . . . . . . . . . . . . 33
QNewAll . . . . . . . . . . . . . . . . . . . . . . . . 33
CONTROLFILE - MATRIX/MESSAGES/FILE-FORWARD . . . . . . . . . 34
MsgArea . . . . . . . . . . . . . . . . . . . . . . . . 34
MsgDrArea . . . . . . . . . . . . . . . . . . . . . . . 34
MsgFrom . . . . . . . . . . . . . . . . . . . . . . . . 34
X_LIST 2.13 - PAGE 3
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
InBound . . . . . . . . . . . . . . . . . . . . . . . . 35
RSPFiles . . . . . . . . . . . . . . . . . . . . . . . . 35
WelcomeMsg . . . . . . . . . . . . . . . . . . . . . . . 35
ThanxMsg . . . . . . . . . . . . . . . . . . . . . . . . 36
DupeMsg . . . . . . . . . . . . . . . . . . . . . . . . 37
ExeMsg . . . . . . . . . . . . . . . . . . . . . . . . . 38
ExtMsg . . . . . . . . . . . . . . . . . . . . . . . . . 38
Lan-Ul . . . . . . . . . . . . . . . . . . . . . . . . . 39
Lan-Wt . . . . . . . . . . . . . . . . . . . . . . . . . 39
Lan-We . . . . . . . . . . . . . . . . . . . . . . . . . 39
Lan-Dr . . . . . . . . . . . . . . . . . . . . . . . . . 39
Lan-Yg . . . . . . . . . . . . . . . . . . . . . . . . . 39
Lan-Th . . . . . . . . . . . . . . . . . . . . . . . . . 39
Lan-Pa . . . . . . . . . . . . . . . . . . . . . . . . . 39
KillReceived . . . . . . . . . . . . . . . . . . . . . . 39
MatrixPath . . . . . . . . . . . . . . . . . . . . . . . 40
ForceIntl . . . . . . . . . . . . . . . . . . . . . . . 40
Outbound . . . . . . . . . . . . . . . . . . . . . . . . 40
HouseClean . . . . . . . . . . . . . . . . . . . . . . . 40
Zones . . . . . . . . . . . . . . . . . . . . . . . . . 41
Forward . . . . . . . . . . . . . . . . . . . . . . . . 41
ForwardMsg . . . . . . . . . . . . . . . . . . . . . . . 42
LotechMailer . . . . . . . . . . . . . . . . . . . . . . 42
Name . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Move . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Tick . . . . . . . . . . . . . . . . . . . . . . . . . . 44
NEW MESSAGE TEXTFILE FORMAT . . . . . . . . . . . . . . . . . 45
WELCOME, THANX, DUPE & EXE-MSG FILE OLD FORMAT . . . . . . . 47
FORWARD MESSAGE FILE OLD FORMAT . . . . . . . . . . . . . . . 48
OPUS LANGUAGE SUPPORT . . . . . . . . . . . . . . . . . . . . 49
PWD SECURITY FILE FOR FILE-FORWARD & DISTRIBUTION . . . . . . 50
TIC SECURITY FILE FOR FILE-ROUTING . . . . . . . . . . . . . 53
FILE DISTRIBUTION CONTROL FILE (XL_TICK.CTL) . . . . . . . . 54
Area . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Hold . . . . . . . . . . . . . . . . . . . . . . . . . . 54
INCLUDED X_LIST UTILITIES . . . . . . . . . . . . . . . . . . 55
MAKEXDIR . . . . . . . . . . . . . . . . . . . . . . . . 55
X_VANVAB . . . . . . . . . . . . . . . . . . . . . . . . 56
ADJUST . . . . . . . . . . . . . . . . . . . . . . . . . 56
OTHER X_LIST UTILITIES . . . . . . . . . . . . . . . . . . . 57
X_NEW . . . . . . . . . . . . . . . . . . . . . . . . . 57
X_LIST 2.13 - PAGE 4
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
OPINTTOP . . . . . . . . . . . . . . . . . . . . . . . . 57
HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
NEW IDEAS FOR FEATURES THAT MIGHT SHOW UP LATER . . . . . . . 64
X_LIST 2.13 - PAGE 5
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
Extremely legal stuff:
----------------------
Copyright (C) 1988-1991 DUGFRISK UNLIMITED, All rights reserved.
Copyright (C) 1989-1991 BIFROST UNLIMITED, All rights reserved.
No part of this manual may be reproduced, transmitted,
transcribed, stored in a retrieval system, or translated into any
language (natural or computer), in any form or by any means,
except as described in the following license without the prior
written permission of Bifrost UNLIMITED.
You are granted a limited license to use the software described
in this manual. The software may be used or copied only in
accordance with the terms of that license, which is described on
the beginning of the next page.
THIS SOFTWARE IS NOT FOR SALE
-----------------------------
X_LIST V2.13 is subject to the following license terms and
conditions.
SINGLE COPY SOFTWARE LICENSE
DUGFRISK & BIFROST UNLIMITED
----------------------------
1.0 X_LIST V2.13 is copyrighted material. You may use it on a
trial basis provided you do not violate the copyright and if
you follow these simple rules. Use of X_LIST V2.13 on a
regular basis requires purchase as described later.
1.1 You may not make any changes or modifications to X_LIST
V2.13, and you may not de-compile, disassemble, or otherwise
reverse-engineer it. You may not rent or lease it to others.
1.2 You may make copies of X_LIST V2.13 only under the terms of
the following section entitled "Limited License to Copy and
use".
X_LIST 2.13 - PAGE 6
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
2.0 LIMITED WARRANTY. DUGFRISK & BIFROST does not warrant that
the functions contained in the software will meet your
requirements or that the operation of the software will be
uninterrupted or error free. The warranty does not cover any
media or documentation which has been subjected to damage or
abuse by you. The software warranty does not cover any copy
of the software which has been altered or changed in any way
by you or others. DUGFRISK & BIFROST are not responsible for
problems caused by changes in the operating characteristics
of the computer hardware or operating system which are made
after the delivery of the software.
2.1 DUGFRISK & BIFROST SHALL NOT IN ANY WAY BE LIABLE FOR
SPECIAL, INCIDENTAL, CONSEQUENTIAL, INDIRECT OR OTHER
SIMILAR DAMAGES ARISING FROM ANY BREACH OF THESE WARRANTIES
EVEN IF DUGFRISK OR BIFROST OR ITS AGENT HAS BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGES.
2.2 The warranties set forth above are in lieu of all other
express and implied warranties, whether oral, written, or
implied, and the remedies set forth above are your sole and
exclusive remedies.
3.0 INTEGRATION. This License constitutes the entire agreement
and understanding between the parties and supersedes any
prior agreement or understanding whether oral or written,
relating to the subject of this License. This Agreement may
only be modified by a written agreement signed by BIFROST.
4.0 If you have a strong feeling, that you have been reading all
this crap before it beats me.
X_LIST 2.13 - PAGE 7
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
LIMITED LICENSE TO COPY AND USE
-------------------------------
You are granted a limited license to copy and distribute X_LIST
Version 2.13 under the following conditions:
- X_LIST V2.13 must be copied in its unmodified form,
complete with the following files:
READ.ME : Release information.
X_LIST.DOC : This documentation.
X_LIST.EXE : Executable file.
MAKEXDIR.DOC : Doc's for MakeXDir...
MAKEXDIR.EXE : Utility program.
X_VANVAB.EXE : Add Avatar color to the listings.
ADJUST.DOC : Documentation for above.
ADJUST.COM : Up-/Down-load adjuster.
XL_ADVAN.CTL : Advanced controlfile.
XL_SIMPL.CTL : Simple Opus controlfile.
XL_OPUS.CTL : Opus sample controlfile.
XL_MAX.CTL : Maximus sample controlfile.
XL_QUICK.CTL : Simple QuickBBS controlfile.
XL_QBBS.CTL : QuickBBS sample control file.
XL_RA.CTL : RemoteAccess sample ctrl. file.
INBOUND.CTL : Another sample control file.
FILEROUT.CTL : Sample Forward control file.
XL_TICK.CTL : Sample Tick Process file.
BADEXT.TXT : Ext message example.
FWDMSG.TXT : Forward message example.
DUPEMSG.TXT : Dupe message example.
NOARCMSG.TXT : Please Arc message example.
THANXMSG.TXT : Thank you message example.
THNX_MSG.TXT : Another Thanx message example.
WELCOME.TXT : Example of welcome message.
- You may change the archive format to any archive type,
as long as none of the files in the archive have been
changed.
- All the files in the archive must be distributed
together.
- No fee, charge or other compensation may be accepted or
requested by anyone without the express written
permission from DUGFRISK or BIFROST unlimited. This
includes disk vendors.
- X_LIST V2.13 may not be distributed in conjunction
with any other product or service without a specific
license from DUGFRISK UNLIMITED or BIFROST UNLIMITED.
X_LIST 2.13 - PAGE 8
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
************************************************************
- In order to use X_LIST V2.13 on a regular basis, you
must at least send a postcard to the following address:
DUGFRISK UNLIMITED
Kristian Ottosen
Mejlgade 69, 4.tv
DK-8000 Aarhus C.
DENMARK
All we ask is to be able to show your postcard to our
grandchildren and say "Look at this one Williamina -
here's another nice postcard from a guy at Papua New
Guinea".
************************************************************
X_LIST 2.13 - PAGE 9
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
INTRODUCTION
X_List v1.00 was only meant to be a fast generator file listing
and making it available for downloading on your Opus 1.03 system.
However with version 2.xx, some unique and superior features were
added... Have a look!!..
o Generation of a public list. All files available for user
download or file-requesting. There are various options
available to give you a large amount of control over what is
being included in this file.
o Output file in a Commafile format for further processing by
your DataBase program, now using a user defined format.
o Various FILES.BBS maintenance functions, such as stripping
^Z's, removing 'missing' files, auto-adopting orphan files
etc.
o Generation of OKFILE.LST in either OPUS or FrontDoor format
(used by Opus/Binkley or Frontdoor for approving file-
requests).
o Sending thank-you messages to uploaders and nasty notes if a
duplicate file is uploaded, or an uploaded file isn't
arc'ed. It will also adjust the users upload, if an unwanted
(dupe or not arc'ed) file is uploaded.
o Sending welcome-on-this-system-hope-you-like-it messages to
new users.
o Generating a little daily reports about the use of your
system as a message to the SysOp.
o Ability to act as a mail-robot, i.e. it can automatically
attach new/changed files for pickup by another system.
o Free-files is a special term. It's simply files that do not
count in your users download.
o Deletion of old versions of a file.
o Multi Zone and Point support.
o Now supports Both OPUS v.1.0x, 1.1x, Maximus 1.02, QuickBBS
v.2.64 and RemoteAccess 0.04.
o Capability to move files from one area to another.
o New Password protected security when Forwarding of files.
X_LIST 2.13 - PAGE 10
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
REQUIREMENTS
To run X_List you need:
An IBM-PC or compatible.
About 200 kb of available memory - More won't hurt.
ANSI.SYS installed in your CONFIG.SYS.
An Opus v1.03 compatible file-system, message-system and
logfile, an Opus 1.1x compatible file-system, a Maximus 1.02
compatible file-system, a RemoteAccess 0.04 file-system
(using QuickBBS Compatible Log and Files.BBS's), or a
QuickBBS v2.64 file system using utilities for importing
messages to QuickBBS message system.
X_list has been tested on a variety of systems,it will also work
with compatible mailers like BinkleyTerm v2.00 and later
versions, and FrontDoor v1.99.
X_List v.2.xx was originally written in Turbo Pascal v4.0, later
ported to Turbo Pascal 5.0 and 5.5.
X_List.Doc was created using Word Perfect v.4.2, later updated
using Word Perfect v.5.0
X_LIST 2.13 - PAGE 11
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
RUNNING X_LIST
Not much to be said about this. You will probably want to run it
on a daily basis, perhaps every time you do your daily
maintenance.
X_List always needs a controlfile, because it uses this to figure
out what to do.
If you run X_List like: "X_LIST" <Enter>, it will only use the
default controlfile name of X_LIST.CTL.
If you want to use another controlfile, you can give it like:
"X_LIST MYCTL". You need not to give an extension to the
filename; X_List assumes the extension .CTL if none is given.
Several control-files are supplied with X_List itself. A simple
one for just making a list of available files, an all-singing
all-dancing version, that shows all the abilities of X_List, and
some other strange setups.
THE CONTROLFILE
All paths must be terminated with a back-slash, like: C:\OPUS\
'%' is the comment-character. When this character is encountered
in the controlfile, the rest of the line is skipped.
There is one statement per line. Most statements only makes sense
if they're listed once in the controlfile.
Unless otherwise stated, all statements are entirely optional.
If a statement is not given, it is assumed to be turned off.
If a statement is given twice the last statement will be active,
this goes for the PrmFile too. An exception from this is the
statements like Forward, Crap, Name etc. which will be stacked.
All statements are case-insensitive. Some of the parameters may
be case sensitive.
You can use standard Dos device-names anywhere. If you want to
let the dupe-report go directly to your printer, your could
specify "DupeReport LPT1" or something of that nature.
X_LIST 2.13 - PAGE 12
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
CONTROLFILE - GENERAL
These are some common things that is needed for overall operation
of X_List.
License: The license number was introduced in ver. 2.03 and
gave those who registered some extra options, this
facility was skipped in ver. 2.04, but the control
statement has been kept for downward
compatibility.
"Licence <LicenceNumber>"
PrmFile: Name of the OPUS v1.03 or OPUS 1.10 parameter file
which contains useful information like BoardName,
LogFile, MatrixPath, SysOp (name of the SysOp),
Zone, Net, Node, Address, InBound, OutBound and
SystemPath. When using this option you may omit
these statements in the X_list controlfile.
X_List will automatically detect if it is a 1.03
or a 1.1x .PRM file, and change the BBS flag.
"PrmFile C:\Opus\BBS.Prm"
SysOp: The name of the SysOp, if not specified, the name
in the PrmFile will be used, if no PrmFile is
selected, the default name will be SysOp.
"SysOp Per Holm"
SystemPath: This statement is used to tell X_LIST where the
system information files are to be located.
The System files are:
Opus 1.03 -> SYSTEM??.BBS
Opus 1.1x -> SYSTEM##.DAT
Max 1.02 -> FILES.DAT (changeable)
RA -> FILES.RA (changeable)
QuickBBS -> (none use 'AreaFile' instead)
"SystemPath C:\Opus\"
When using Maximus and RemoteAccess you may add a
filename after the path to change the default name
of the system files..
"SystemPath C:\Max\FILES.DAT"
X_LIST 2.13 - PAGE 13
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
AreaFile: QuickBBS area description file. The file should
tell where to find the file areas on a QuickBBS
system, and point to the QuickBBS file area file.
When used the System??.BBS/System??.DAT or the
FILES.RA files will not be used, unless you use
the MsgArea <areanumber> option. The QuickBBS
areas will be numbered staring with area 1 for the
first line, 2 for the second etc.....
"AreaFile C:\QBBS\FLSEARCH.TXT"
XListData: This creates a small file which is used for
storing such things as when X_List was last run
etc,etc.,. Normally you have no need to mess with
this file, but you can delete it to force X_List
to scan your logfile from the beginning if needed.
Please note, that if the file is missing, the
built-in mailrobot (if enabled) will not attempt
to send any files. This file also defaults to
NUL:. If not given, the logfile will be scanned
from the start each time, and you will be unable
to use the MailRobot (below).
"XListData C:\X_List\X_List.Dat"
XLogFile: When running X_List early in the morning (when
even SysOp's do feel tired) it is nice to have a
log of what really happened. Use this statement to
get an OPUS compatible logfile..
"XLogFile C:\X_List\X_List.Log"
** WARNING: do not use a logfile used by 'LogFile' **
X_LIST 2.13 - PAGE 14
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
LogLevel: Use this to get a more or less informative log,
use a value between 0 and 6. "LogLevel 6"
0 : No log info.
1 : '!'
2 : '!','*'
3 : '!','*','+'
4 : '!','*','+',':'
5 : '!','*','+',':','#'
6 : '!','*','+',':','#',' '
"LogLevel 5"
FileMode: This control statement are made for use with some
LAN's and Multi-task programs. The basic idea is
to change the method a file are opened, by default
Turbo Pascal opens all files in Read/Write mode
(FileMode 2), this does cause some LAN and Multi-
task programs to proces a read error if to tasks
or workstations wishes to access the same file...
The statement need a value for the FileMode to be
used, please refer to you LAN manual for mode
information.
"FileMode 2 % R/W mode"
"FileMode 0 % R/O mode"
BBS: This control statement is used to tell X_List
which BBS type it must support. The default BBS
type is 'OPUS'. The BBS type will be updated by
the PrmFile command, to the correct OPUS version,
if you want to change this place one of these
commands after the PrmFile command:
"BBS OPUS % Opus ver 1.03"
"BBS O % Opus ver 1.03"
"BBS OPUS1.10 % Opus ver 1.1x"
"BBS 1 % Opus ver 1.1x"
"BBS Maximus % Max version 1.02"
"BBS M % Max version 1.02"
"BBS QuickBBS % QuickBBS mode"
"BBS Q % QuickBBS mode"
"BBS RemoteAccess % RemoteAccess"
"BBS R % RemoteAccess"
X_LIST 2.13 - PAGE 15
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
Mailer: Lately I discovered that FrontDoor does not use
the same OkFile format as OPUS and Binkley, this
statement may be used to generate a frontdoor
compatible okfile, with time the statement will
get a more general meaning. the default is "OPUS":
"Mailer OPUS % Opus ver 1.03"
"Mailer O % Opus ver 1.03"
"Mailer OPUS1.10 % Opus ver 1.1x"
"Mailer 1 % Opus ver 1.1x"
"Mailer RemoteAccess % RemoteAccess"
"Mailer R % RemoteAccess"
"Mailer Binkley % Binkley Term"
"Mailer B % Binkley Term"
"Mailer FrontDoor % FrontDoor"
"Mailer F % FrontDoor"
BoardName: Use this keyword to state the name of your system.
All characters including % (comment) are allowed
after the BoardName control statement.
"BoardName Asgaard BBS."
*** WARNING: No Comment on Boardname Statement ***
Address: This may be used to tell X_List your Full address,
you may chose to use the Point, Node, Net and Zone
statements instead, they do the same.
"Address 2:230/22"
"Address 2:230/22.3"
You may now specify Aka addresses, these are used
when forwarding files or messages to other Zones
that you are a member of:
"Address 2:230/22 % FidoNet"
"Address 27:1345/100 % SigNet"
"Address 97:9451/4 % EggNet"
Zone: Tells X_List what zone you're in. (Unstable)
This statement may be removed in a later release.
"Zone 2"
X_LIST 2.13 - PAGE 16
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
Net: Informs the program of your netnumber. (Unstable)
This statement may be removed in a later release.
"Net 230"
Node: And your nodenumber. (Unstable)
This statement may be removed in a later release.
"Node 22"
Point: If you are a point state your pointnumber here.
(Unstable) may be removed in a later release.
"Point 1"
Note: If you do not wish any point address shown
just ignore this control statement.
Drives: A list of drives to check for free space.
"Drives CDEFIJ"
Default is drives CDEFGHIJ. Last drive is Z
This command should be used instead of the
MaxDrive statement.
MaxDrive: The maximum number of drives to check for free
diskspace, "MaxDrive 3" will check drive C,
"MaxDrive 4" will check drive C and D.
"MaxDrive 0" will not check any drives.
This Control statement has been kept for downward
compatibility with older versions of X_List. The
statement may be removed in future versions.
Debug: Enable the internal debugger, just in case.
Hindustan: Proper generation of messages cannot be expected
if this is set to a wrong value. Please refer to
the sample controlfiles for explanation of usage.
X_LIST 2.13 - PAGE 17
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
CONTROLFILE - PUBLIC LIST
The public list is the file that shows all files available for
download on your system. These statements need not be used, but
you can gain a better control over the program if you do.
OutFile: X_List needs to know where to put the resulting
public list (list of all files on the board), and
what to name it.
"C:\FILE\1\ASG_LIST.TXT"
The outputfile defaults to NUL: - I.e. no
outputfile at all.
You may use the X_VANVAB program to add some
avatar colors to this file for use in a menu on an
OPUS system.
NewsList: X_List may make a separate list containing only
the latest files arrived at your BBS.
"NewsList F:\MISC\ASG_NEWS.TXT"
You may use the X_VANVAB program to add some
avatar colors to this file, if you run an OPUS
system..
CommaFile: As well as the above file, you may want another
file for further processing by other programs.
This states the name of an outputfile in DBase III
(or Basic) format. eg. a raw file without
comments, with each field separated by a comma
(,). The record-layout for this file can be found
in the resulting commafile file.
"CommaFile C:\DB\CommaLst.TXT"
X_LIST 2.13 - PAGE 18
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
CommaFormat: If you don't like the default commafile format,
you may define your own format of the CommaFile
The following words may be used:
%file : Name of the file.
%size : The size of the file.
%area : Area number of the file.
%comment : Insert file comment in DBASE
file. *** VERY SLOW ***
%year : The year part of the file date.
%month : The month part of the file date.
%day : The day part of the file date.
%hour : Hour part of the file time.
%min : minute part of the file time.
%sec : Sec. part of the file time.
%zone : Your zone number.
%net : Net number.
%node : Node number.
%point : Point number.
%address : The full Zone:Net/Node.Point
address.
"CommaFormat '%file','%area','%size'"
Index: Future utilities from Dugfrisk unlimited and
Bifrost unlimited may require an X_list generated
Master-index file. This is made by specifying the
path to this file and the day of the week when it
should be written.
0=Sunday..6=Saturday and 7=All.
The file will be named XXXXYYYY.IDX where XXXX and
YYYY are net and node number as 4 HEX digits.
"Index 5 C:\OPUS\DANELIB\"
Will write an index every friday!!
The format of this file will be described later in
this document.
MaxFiles: How many files do you expect to have on your
system at any time? Should be stated. It is set to
a default value of 1500 files. It is also used for
allocating memory for sorts etc. The maximum limit
is 10.000 files.
"MaxFiles 1500"
X_LIST 2.13 - PAGE 19
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
Header: If you want a header at the start of the public
list, you can give a path to a file here. It could
be the LOGO.BBS file. For instance:
C:\OPUS\MISC\LOGO.BBS. Then LOGO.BBS would be the
first thing the user will see, when viewing your
total filelist. Useful for communicating with the
typical download freak. At least you should write
the name of your board here, since X_List defaults
to not putting any header in the list at all. You
may use wildcards in this statement, this will
give you a random header file (will choose one of
Max 10)..
"Header C:\Opus\Misc\Logo?.BBS"
"Header C:\Opus\Misc\Logo.BBS"
Footer: You may also insert a text file in the end of the
Public list using the Footer statement.
"Footer C:\Opus\Misc\Logo?.BBS"
"Footer C:\Opus\Misc\Logo.BBS"
Level: Only areas that allows users with this level or
below, should be written in the public list.
Usually you will not want files intended for
SysOp's only to be included in a public file, so
you could use: "Level Priv" to include all areas
with access for privileged or below users. The
default is to use a level of normal. Levels known
by the program is: 'Twit', 'Disgrace', 'Limited',
'Normal', 'Worthy', 'Privil', 'Favored', 'Extra',
'Clerk', 'AsstSysop' and 'SysOp'.
QuickBBS and RemoteAccess users may use a value in
the range 0 - 65535 for user levels. (the usable
levels are described in the QuickBBS and
RemoteAccess manuals). Eg. "Level 32000"
"Level Extra"
"Level 32000"
X_LIST 2.13 - PAGE 20
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
Skip <nn>: This tells X_List to skip a particular area,
regardless of what level it has. Used for
overriding the "Level" keyword above.
"Skip 23"
This option should now work within QuickBBS mode,
the areas from the FLSearch file will be numbered
from Area one and follow the linienumbers in the
file..
Skip Barricaded: Use this option to tell that you don't want
to include barricaded areas in the listing,
regardless to what level they require.
** OPUS/MAX/RA ONLY **
Skip Text: Strip all text-only lines from the FILES.BBS
files. eg. produce a public list with a file
listed on every single line. The Skip Text
statement may be reversed for a single area using
'Show <area> Text'.
Skip Missing: When generating the Public list you may decide
that all those missing files should not be in the
list. This option will leave them out of the
Public List. This statement may be reversed for a
single area using 'Show <area> Missing'.
Show: The exact opposite of "Skip". It will include an
area in the public list regardless of level.
"Show 23"
You may also reverse the 'Skip Test' and 'Skip
Missing' statements for a one or more areas by
using one or more lines like the following:
"Show 23 Missing"
"Show 24 Missing"
"Show 23 Text"
This option should work within QuickBBS mode, the
areas from the FLSearch file will be numbered from
Area one and follow the linienumbers in the file..
X_LIST 2.13 - PAGE 21
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
First: Well, Kristian has put all his file-areas in the
range 50-99, that is because he doesn't want
X_List wasting precious time wading through areas
1-49. This statement tells what SYSTEMnn.BBS/.DAT
file, Area.Dat or FILES.RA entry to use.
** Not available for QuickBBS **
"First 1"
Last: Tells which is the last SYSTEMnn.BBS file or last
area record to be looked into.
** Not available for QuickBBS **
"Last 99"
MaxAreas: When using Maximus, it is possible to have
filareas described by character like AA BZ etc.
Since X_List is limited to 255 areas described by
numbers 1 to 255, we have to translate the Maxmus
areas above 99 to something X_List will be able to
handle... The MaxAreas statement will start
numbering the special areas beginning with area
number 100... X_List will accept one or more
MaxAreas control lines.. In commands like Skip,
Adopt and other commands using an area number, you
have to use the number of the Maximus areas,
instead of the characters.
"MaxAreas AA AB AC BA B1"
"MaxAreas ZA ZB ZC"
MarkLast: X_list defaults to mark last months file with a
'*' in the Opus way.
You may change the number of days using MarkLast.
"MarkLast 30"
EuroDate: Use European date form ('DD/MM-YY') in the Public
filelists.
Lan-Ud: Update info in the Public List.
"Lan-UD Updated by % X_LIST V2.13"
X_LIST 2.13 - PAGE 22
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
Lan-Fa: The area information in each area header in the
public list.
"Lan-FA File Area # % File area # (header)"
Lan-Fr: This line will be inserted just below the area
header if the files are available for filerequest.
"Lan-FR (Matrix filerequest possible)"
Lan-Fp: If the area is password protected this message
will be inserted under the Area header.
"Lan-FP (You need a password to f.req here)"
Lan-Mi: If a file is not available this message will be
inserted instead of the file date.
"Lan-MI Disappeared % Missing files"
Lan-Fl: And this in the and of the Public list.
"Lan-FL titles listed % Total no of files"
Lan-NF: If you wish to change the comment in top of the
NewsList file, you need to use this statement.
"Lan-NF New files: %1 day period %2 - %3"
The following Meta strings may be used:
%1 : Number of days to be included, the value
is entered using the MarkLast statement.
%2 : First date of the period.
%3 : The current date...
X_LIST 2.13 - PAGE 23
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
CONTROLFILE - AREA MAINTENANCE
X_List runs through every FILES.BBS file on your system, so why
not do some housekeeping while we're at it?
Rewrite: You may have noticed that programs such as Fido-
Fam insists on putting a Ctrl-Z at the end of
every modified FILES.BBS. Whenever a file gets
added to this FILES.BBS by Opus (beyond the Ctrl-
Z) your users won't see it, because Opus stops
reading it when it encounters the Ctrl-Z.
This cures the problem by writing a new FILES.BBS
without ^Z's while reading the old one. Note that
all lines after a ^Z is lost. This is a temporary
limitation and will be resolved in a future
release.
"Rewrite % Rewrite all areas"
You may also choose to do a rewrite in a few
areas, or disable it for some..
"Rewrite 2 % Rewrite in area 2"
"Rewrite 4 - % Skip rewrite of area 4"
Adopt: X_List may find some orphan files in your
fileareas. With this statement you can make it add
these parent-less files to the FILES.BBS, thus
making them available for download by your users.
It may have undesirable results, though...
Of course it will not insert files that should not
be available for downloading. This is: FILES.BBS,
FILES.BAK, DIR.BBS, DIR.BAK and X_LIST.DIR.
"Adopt % Adopt all areas"
You may also choose to do an adopt files in a few
areas, or disable it for some..
"Adopt 2 % Adopt in area 2"
"Adopt 4 - % Skip adopt in area 4"
X_LIST 2.13 - PAGE 24
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
ReFlow: X_LIST will tidy your FILES.BBS in different ways
by splitting descriptions too long to be displayed
by Opus<Tm> into separate lines with spaces
inserted to get the indent right
"ReFlow % Reflow all areas"
You may also choose to do a rewrite in a few
areas, or disable it for some..
"Reflow 2 % Reflow in area 2"
"Reflow 4 - % Skip reflow of area 4"
RemMiss: If you want to add style to your FILES.BBS's you
can use this option to remove any lines in them
that states a file is missing. Use however with
care, as your descriptions of any missing files
will be gone!
"RemMiss % Reflow all areas"
You may also choose to do a rewrite in a few
areas, or disable it for some..
"RemMiss 2 % Remove Miss. files in area 2"
"RemMiss 4 - % Keep Missing files in area 4"
Crap: This option informs X_List that you don't want to
keep the listed file. If it sees it while wading
through the areas, it will be erased. This is
useful for scratching things such as DIR.BAK,
FILES.BAK, ZAXXON.ARC (non-PD) etc. If you want to
zap more than one file, you can give this
statement several times. The filename given should
not include a path.
"Crap Dir.Bak"
"Crap Masturba.Arc"
"Crap *.GIF"
**** Warning: Watch out for Wildcards ****
Secure: When running through the Areas X_List will make a
directory Files.Gbs to ensure that noone just
uploads a Files.GBS..
** Used to fix an OPUS 1.03 and 1.1x bug **
X_LIST 2.13 - PAGE 25
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
ZapZero: While speeding through the areas , X_List may
delete empty files from the directories
(unsuccessful uploads etc.).
DupeReport: On a large system, there will typically be above
1000 files available for download. This makes it
fairly hard to ensure that no duplicate files are
to be found around in the areas. With this option
you can specify a filename which will end up being
a nice report of duplicate files for the SysOp
enabling you to cut down the use of your precious
diskspace. A file is called a DUPE if there is
another file with the same name (the extension may
be different), and the smallest file is less than
20% smaller than the bigger one. This is not the
most safe criteria, but will work most of the
time. Here is an example where X_list will say
that two files are dupes but they are NOT:
OPINT102.ZIP 57014 bytes.
OPINT102.5IP 57461 bytes.
This dupe criteria has been changed to be like
this staring with version 2.10 this version,
because of all the new packing methods that has
entered the scene these days.
DupeReport [/M] [/C] [/D] [<DupeFile>]
/M : Send report as Msg to SysOp.
/C : Mail report to CoSysOps.
/D : Delete file after sending.
"DupeReport /M /C /D C:\Tmp\Dupes.$$$"
OrphanReport: If used, this will create a file to be used for
writing a report of orphan files on your system.
Useful if you want to check out floating files
before making them available for download.
OrphanReport [/M] [/C] [/D] [<OrphanFile>]
/M : Send report as Msg to SysOp.
/C : Mail report to CoSysOps.
/D : Delete file after sending.
"OrphanReport /M /C /D C:\Tmp\Orphan.$$$"
X_LIST 2.13 - PAGE 26
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
KeepLatest: Say you want to delete old copies of the nodelist
updates - and only keep the latest four:
"KeepLatest 4 C:\FILE\NODELIST\NODEDIFF.A*"
X_LIST will then look at all the matching files
and delete these files except those 4 with the
latest dates.
This option should be used with great care, a
typing error might cause you to loose some
important files...
Touch: Touch is simply the good old thing ,it stamps
current date and time on existing files. This
version doesn't use wildcard like '*' or '?'.
Usage:
"Touch E:\OPUSFILE\INFO\ASG_LIST.ARC"
** WARNING: NEVER TOUCH THE FILES X_LIST IS WORKING ON **
AdoptComment: When adopting new files your X_LIST might add a
comment, this can be done like this:
"AdoptComment (description missing)"
Convert: And you may replace special characters in the
public list and FILES.BBS.
The below translations are useful in Denmark:
Convert { æ % Ascii 145 "ae"
Convert | ¢ % Ascii 155 "oe"
Convert } å % Ascii 134 "aa"
Convert [ Æ % Ascii 146 "AE"
Convert \ ¥ % Ascii 157 "OE"
Convert ] Å % Ascii 143 "AA"
Convert ^F å
Convert ^Q æ
Convert ^[ ¢
Note that some Download Counters use one or more
of the above characters, and this option may cause
the Download counter to get confused by changing
these characters..
X_LIST 2.13 - PAGE 27
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
CONTROLFILE - OKFILE GENERATION
If you want to, X_List can create an OkFile for you too. An
OkFile is the file that Opus,Binkley and FrontDoor uses for
approving file-requests. X_List will include each area that is in
the public list in the OkFile too. It will for the OPUS/Binkley
OKFILE look something like: "D:\FILES\OPUSUTIL\*.*" Each line
matches one of the File areas.
OkFile: This names the resulting list of approved files
for file request. Depending on the mailer used,
this file will be in either Opus/Binkley or
FrontDoor format...
"Okfile C:\NET\OKFILE.LST"
OkHeader: You may have some files or directories in your
OKFILE.LST that are not in any of your
SYSTEMnn.BBS/SYSTEMnn.DAT/AREA.DAT/FLSEARCH.CTL
files. This may include your netfilearea, your
upload area or the like. This statement names a
file which is written to the OkFile before all of
the regular areas. This file must have the same
structure as the OKFILE itself. Check you mailer
documentation for more information.
"OkHead C:\Ctl\OkHead.TXT"
Password All: When generating an Opus/Binkley compatible OKFILE
you may add a password to all file areas. Note,
that in the password the case IS significant!
"Password All SECRETS"
** Not available for The FrontDoor Mailer **
Password nn: When generating an Opus/Binkley compatible OKFILE,
you may add/remove/change the password for a
single area.
"Password 55" Remove password
"Password 56 SECRET" Add/Change password
** Not available for The FrontDoor Mailer **
X_LIST 2.13 - PAGE 28
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
Magic: Use this option to make some often updated files
available using a magic filename. To be used like
this.
"Magic Nodelist C:\File\NetInfo\Nodelist.A*"
"Magic Nodediff C:\File\NetInfo\NodeDIFF.A*"
"Magic Fnews C:\File\NetInfo\Fnews???.Arc"
"Magic Secret C:\Pvt\Secret*.* Password"
** Note Passwords does not work along with **
** the FrontDoor Mailer. **
X_LIST 2.13 - PAGE 29
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
CONTROLFILE - LOGFILE ANALYSIS
If you want to, X_List will send various messages to your users,
depending on what they have uploaded to your board. It can also
send welcome messages to new users.
It looks in the Opus/Maximus/QuickBBS/RA logfile for the required
information, and all logging levels ought to work.
There are sample messages supplied in the distribution arcfile.
Note the X_List Opus 1.10 log analysis will only work if the
SysOp language are English...
LogFile: This is the log file we want to analyze. The file
must be like an OPUS log file or a QuickBBS log
file. RemoteAccess must use a QuickBBS compatible
log file. You may add up to 10 LogFile statements.
"LogFile C:\Opus\Opus.Log"
"LogFile C:\Max\Max.Log"
Upload: When analyzing an OPUS/Binkley compatible log
there might be some external programs adding some
other upload descriptions instead of 'UL-' like
the OPUS, Binkley uses 'Received-'.
"Upload +Received- % Use Binkley Uploads."
"Upload =RECV % Use BIOPUS entrys too"
Note the first character which is the log level
indicator (eg. '=').
Download: And for the Download we have excactly the same
facility:
"Download +Sent- % Use Binkley Downloads"
"Download =SEND % And BIOPUS"
DailyReport: If you want it, we can send you a message every
day about the usage of your system since X_List
last was run. It will be sent as a private message
to 'MsgFrom' (above) and end up in area 'MsgArea'
(above).
X_LIST 2.13 - PAGE 30
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
SessionReport: When processing mail, it is nice to check if all
mailsessions during the last period was running as
they should... This statement will enable some
nice report features..
SessionReport [<Flags>] [<Sessionfile>]
<Flags> : [/M] [/C] [/D] [/A] [/I] [/O]
/M : Mail the Report.
/C : Copy for CoSysOps....
/D : Delete file after mailing.
/A : Report all sessions. (Default)
/I : Report incoming sessions only
(other system dialing)
/O : Report outgoing sessions only
(this system dialing)
If no SessionFile is specified, the SessionReport
will be placed in the DailyReport....
"SessionReport"
"SessionReport /M /D /O D:\Tmp\Session.$$$"
X_LIST 2.13 - PAGE 31
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
CoSysOp: You may wish to send a copy of the daily report to
your CO-SysOp Mrs Ackermann.
"CoSysOp Mrs. Ackermann"
And to the other one who is a point somewhere.
"CoSysOp 2:230/22.3 Cr. Ackermann"
To use this option you need the Matrix path set to
the NetMail directory or the AREA: tag set, this
is described later in this document.
CoSysOp [<Flags>] [<Node>] <Name>
<Flags> : Report Types for this CoSysOp
(Default are All report Types)
/R : Daily Report
/S : Session Report
/D : Dupe Report
/O : Orphan Report
<Node> : Nodenumber of the CoSysOp (Optional)
<Name> : Name of the CoSysOp
Include: Normally X_List checks the public list to see if
an uploaded file is a dupe. However, if your
upload area is not included in the public list,
you can use this statement to inform the program
where to find newly uploaded files.
give a path, and a wildcard specification -
Exactly as with the Dos DIR command.
"Include C:\Uploads\*.*"
"Include C:\Inbound\*.*"
"Include C:\Gif\*.Gif"
X_LIST 2.13 - PAGE 32
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
FreeFiles are files for downloading that won't have any influence
on your users download-amount. Often, you don't want files such
as the Opus end-users manual to count in the upload:download
ratio.
X_List can create a file, that states what adjustments should be
should be made to the User file. This file is also used for
subtracting uploaded dupefiles from the users upload amount.
Due to the proposed changes to the structure of the USER file,
the actual adjustment will be made by an external program
'ADJUST' - It should be included in the X_List archive.
UserAdjust: Gives path and filename to the user adjustment
controlfile. The format of this file is described
in the ADJUST.DOC file.
FreeFile: States a file that is 'free' to download. The size
of this file will be put in the controlfile above
used by the adjuster-program. This statement can
be given as many times as needed.
QNewAll: When running in QuickBBS mode, you have two
methods for checking for new users, either you
have to be sure if the user is registered, or you
may write welcome messages to users who are not
yet in the UserFile.
"QNewAll % Write to all possible new users"
X_LIST 2.13 - PAGE 33
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
CONTROLFILE - MATRIX/MESSAGES/FILE-FORWARD
MsgArea: This should be the number, path or area name of
the message area, that all X_List messages are put
in. Currently, all messages sent will be made
private, regardless of what attribute the
corresponding area have set. The messages
generated will be the .MSG file format used by
OPUS 1.03. Here are some examples:
"MsgArea 1 % Use Opus Area one for messages"
"MsgArea c:\Msg\Local\ % or the Path"
When using a QuickBBS or RemoteAccess system you
place the messages into a QBBS/RA compatible
message database.
"MsgArea c:Ra\Msgs\ 1 % Add to area 1"
You may also chose to generate .PKT files to be
placed in the inbound area for tossing to the
correct area. Here is how to handle this:
"MsgArea AREA:LOCAL % Or Echo Mailname .PKT"
"MsgArea AREA: % This is for the Matrix Area"
*** Note that if you are using the AREA: options
you must set the 'InBound' Directory, and 'AREA'
must be in uppercase.
MsgDrArea: If you want your Daily report in another area than
MsgArea you may use this statement, the usage is
the same as for the MsgArea statement.
"MsgDrArea AREA:SYSOP" or "MsgDrArea 1"
MsgFrom: This should be the SysOp's name and is used for
putting in the "From:" field of every generated
message. If this control statement is not
specified the name of the Sysop statement will be
used. The default SysOp name is "SysOp".
X_LIST 2.13 - PAGE 34
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
InBound: When running a BBS which do not use the Opus .MSG
format you may use the 'AREA:' option to send the
messages. This control statement must be used to
tell X_List where to place the .PKT files.
"InBound C:\Traffic\In"
RSPFiles: When requesting files on a Binkley system, you may
get a response file, X_LIST is able to move these
.RSP files into a matrix message (to use this
statement both the MatrixPath and the Inbound path
must be specified).
"RSPFiles"
The below textfiles are pure ASCII and can be created with any
ASCII editor, such as EDLIN <sigh>.
WelcomeMsg: X_List can make a nice welcome-message. for your
new users. When scanning the logfile X_List will
check if a user is online for the first time, and
if this is the case the user will get a welcome
message, when using this statement..
If you use wildcards in the filename, X_List will
pick one of those files for this session.
"WelcomeMsg C:\Opus\X_List\Welcome.Txt"
"WelcomeMsg C:\Opus\X_List\Welcome?.Txt"
If you use OPUS 1.1x, you may wish to use the
language support, for more details see the section
OPUS LANGUAGE SUPPORT on page 45.
"WelcomeMsg C:\Opus\X_List\Welcome?.#xt"
The format of the WelcomeMsg file will be
discussed below.
X_LIST 2.13 - PAGE 35
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
ThanxMsg: Name of the file(s) that will be sent as a message
to all uploaders (except files not arc'ed,
duplicate files and special Extensions - see
below).
If you use wildcards in the filename, X_List will
pick one of those files for this session.
"ThanxMsg C:\Opus\X_List\ThanxMsg.Txt"
"ThanxMsg C:\Opus\X_List\Thanx*.Txt"
If you use OPUS 1.1x, you may wish to use the
language support, for more details see the section
OPUS LANGUAGE SUPPORT on page 45.
"ThanxMsg C:\Opus\X_List\Thanx*.#xt"
The format of the ThanxMsg file will be discussed
below.
X_LIST 2.13 - PAGE 36
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
DupeMsg: Sometimes users upload files that already exists
on the system. This statement can be used for
sending a nasty note, telling them to use L)ocate
before uploading any more files. The full filename
is compared, however there is some special things
taken into account:
A file will be considered a DUPE if there is
another file with the same name (the extension may
be different), and the smallest file is less than
20% smaller than the largest one. This is not the
most safe criteria, but will work most of the
time. Here is an example where X_list will say
that two files are dupes but they are NOT:
OPINT102.ZIP 57014 bytes.
OPINT102.5IP 57461 bytes.
If you use wildcards in the filename, X_List will
pick one of those files for this session.
"DupeMsg C:\Opus\X_List\DupeMsg.Txt"
"DupeMsg C:\Opus\X_List\DupeMsg.Tx?"
If you use OPUS 1.1x, you may wish to use the
language support, for more details see the section
OPUS LANGUAGE SUPPORT on page 45.
"DupeMsg C:\Opus\X_List\DupeMsg?.#xt"
The format of the DupeMsg file will be discussed
below.
X_LIST 2.13 - PAGE 37
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
ExeMsg: You may want to teach your users that only arc'ed
files are welcome on your system. This textfile
will end up as a msg. to all uploaders who have
sent a file with .EXE, .COM, TXT or .DOC
extension. Unfortunately it is no longer possible
to check for selfextracting archive programs any
more. The reason for this is that there are just
to many different archive systems.
If you use wildcards in the filename, X_List will
pick one of those files for this session.
"ExeMsg C:\Opus\X_List\ExeMsg.Txt"
"ExeMsg C:\Opus\X_List\ExeMsg.Tx?"
If you use OPUS 1.1x, you may wish to use the
language support, for more details see the section
OPUS LANGUAGE SUPPORT on page 45.
"ExeMsg C:\Opus\X_List\ExeMsg?.#xt"
The format of the ExeMsg file will be discussed
below.
ExtMsg: If you have some special extension you like or
dislike you may write a special message to those
uploading such files.
If you use wildcards in the filename, X_List will
pick one of those files for the current session.
"ExtMsg MAC C:\Opus\X_List\MacMsg.Txt"
"ExtMsg GIF C:\Opus\X_List\GifMsg.Tx?"
If you use OPUS 1.1x, you may wish to use the
language support, for more details see the section
OPUS LANGUAGE SUPPORT on page 45.
"ExeMsg MAC C:\Opus\X_List\MacMsg.#xt"
The format of the ExtMsg File will be discussed
below.
X_LIST 2.13 - PAGE 38
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
Lan-Ul: If someone uploads a dupe he will get a message
with a subject like this:
"To send ABC.AR1 is a waste of time"
The first part of the text is selected like this:
"Lan-UL To send % Dupes part I"
Lan-Wt: And here is the second part:
"Lan-WT is a waste of time % Dupes part II"
Lan-We: Subject line for the welcome message to the new
users.
"Lan-WE Welcome to Asgaard BBS!! % Welcome User"
Lan-Dr: Subject line for the daily report from X_List.
"Lan-DR Your daily report % Daily Report."
Lan-Yg: Subject line for the Forward messages.
"Lan-YG You got yourself a % Forward Message"
Lan-Th: Subject for the thanx for the upload message.
"Lan-TH Thanks for sending % ThankYou message"
Lan-Pa: Subject for the message sent when the user did not
ARC the uploaded files.
"Lan-PA Try Arc'ing % Exe/Com uploads"
KillReceived: X_LIST may delete it's own messages when received.
This does not include messages written by X_LIST
versions below Ver 2.04.
When using messages to be sent as NetMail, these statements are
needed to generate a proper origin line, and addresses. If your
messages are local-only, then you can leave the below commented
out - Then only a tear line will be put in the message.
X_LIST 2.13 - PAGE 39
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
MatrixPath: The path to your Matrix message area.
This is used with the Forward command if you send
a forward message, or if your Co-SysOp has his own
nodenumber (Either as a point or a board).
"MatrixPath 90 % Use message area 90"
"MatrixPath c:\Msg\Local\ % Path to .MSG dir."
"MatrixPath AREA:LOCAL % Echo Mailname for .PKT"
"MatrixPath AREA: % This is for the Matrix Area"
"MatrixPath C:\RaMsgs\ 90 % RA/QBBS msg base"
*** Note that if you are using the AREA: options
you must set the 'InBound' Directory, and 'AREA'
must be in uppercase.
ForceIntl: When writing messages for other Zones, X_List will
insert a ^aINTL with some additional information.
If you are a member of more than one Zone
(normally different networks), you may force
X_List to insert the ^aINTL information in all
NetMail messages
"ForceINTL % always Insert INTL information"
X_List also have a built-in MailRobot! (Another program to
scratch!). It is fairly simple, and works this way: Each file
listed will have its modification time compared with the time
X_List was last run - Any new (or changed) files that have
entered the system since last run, will be file-attached by
appending (or creating) a .HLO file in your outbound area for
each subscribing system. X_List wants to know:
Outbound: This is the path to your holding (outbound) area.
HouseClean: Clean out in the outbound area, delete bad dialup
files (*.$*) and any sent .PWD files.
X_LIST 2.13 - PAGE 40
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
Zones: When using Binkley v2.40 as mailer, you have the
opportunity to use multi zone support, using extra
directories like this (in zone two):
C:\OutBound\ < Standard Zone two
C:\OutBound.001\ < Zone one.
C:\OutBound.FFF\ < Zone 4095
If not used you must use the Zone Gate to send
messages/Forward files..
Forward: The name of the file(s) to file-attach for other
systems. Usage like:
Forward <file> <Dest>[,<Dest>[..]]
<Dest> : [<Flag>]<Addr>[!<Pwd>>]
<Flag> : C = Crash, D = Direct, N=Normal &
and H = Hold (Default)
<Addr> : [<Zone>:]<Net>/<Node>[.<Point>]
<Zone> : Destination Zone (the Zones
statement must be enabled)
<Net> : Destination net.
<Node> : Destination node.
<Point>: Destination point. <Will force
LotechMailer Mode>
<Pwd> : Password for destination node.
"Forward C:\NETF\INFO.* C230/101,2:231/34.13".
Note the full Zone:Net/Node.Point address.
The above will file-attach any files matching
NODEDIFF.* in the C:\OPUS\NETF directory to
230/101 and 2:231/34.13. Please note, that each
node-number should be separated by a comma (,) -
Not a space or anything else.
You can specify as many forward statements as you
like, and you may specify up to 20 nodes on each
forward statement, but the length of each forward
line may not exceed 255 characters.
If any point address has been specified,
LotechMailer mode will automatically be enabled.
X_LIST 2.13 - PAGE 41
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
ForwardMsg: The path to the forward message to be sent
following a file when using the LotechMailer
command. If you decide to use wildcards in the
filename, X_List will pick one of those files for
this session. Here are some examples:
"ForwardMsg C:\OPUS\CTL\FORWDMSG.TXT"
"ForwardMsg C:\OPUS\CTL\FWDMSG*.TXT"
The format of the ForwardMsg file will be
discussed later on page 45 and page 48.
LotechMailer: When forwarding files to other systems you might
want to write a message to the SysOp that he has
received the file. This command makes X_list
create messages with file attaches instead of .HLO
files in the outbound directory.
X_LIST 2.13 - PAGE 42
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
Name: When using the ForwardMsg the messages sent with
the file will by default be sent to SysOp. You may
use this statement to change 'SysOp' the name of
the sysop of one or more nodes by adding one or
more statements like this:
"Name 2:230/101 Mik Tuver"
"Name 231/34.13 Kristian Ottosen"
You may also choose to disable the Message for one
or more nodes (unless it is an '.XMG' file or the
LotechMailer Statement has been enabled:
"Name 2:230/22 /N Per Holm"
"Name 2:231/34 /N Johnny Odgaard"
IF You wish to force a LotechMail and LotechMailer
has been disabled for a given node, you may add
the /L to the line:
"Name 2:230/901 /L Henrik Dermund"
If you decide to send Secured Forwards for a
specified node, you need a password for the node,
this is done by using the Name statement like
this:
"Name 2:230/101 /PTEST Mik Tuver"
'Name [/S[<PWD>]] [/N] [/L] <Name>'
/N Do not send Forward Messages.
/L Do File Attach for this node.
/P Send Security file.
/P<PWD> Send security file with password.
<Name> Name of the receiver.
X_LIST 2.13 - PAGE 43
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
Move: Move or copy a file from one directory to another.
'Move E:\In\Fnews*.arc D:\File /T /F /X /S<Node>
/P<PWD> /C<Txt>'
/T Touch the file after moving it.
/F Forward the file after moving (don't
check the date).
/X Copy the file instead of moving it.
/N Move new files. Move file if it is dated
after last X_List session.
/S<Node> Check file i inbound for security,
the sender must be <Node>
/P<PWD> Security Password, the password must
match the one in the .PWD file.
/C Insert file into FILES.BBS in the
destination area, without any comment.
/C<TXT> Comment the file with <TXT> when adding
it to the FILES.BBS in the destination
area. Don't start the text with a space.
** /C must be the last option in this line **
Tick: If you are the end user in any Software
distribution network, like SDS or PDN, you may
enable this option, X_List will now process a Tick
compatible Tick.CFG (look at page 50 for
information on the special tick control file)..
The current version of X_LIST does NOT support
FLEA files.
X_LIST 2.13 - PAGE 44
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
NEW MESSAGE TEXTFILE FORMAT.
When designing the messages for the users, you have a powerful
tool, the meta-strings.
The following meta-strings are available in this version:
%name Name of the user/receiver.
%fname Firstname of the user/receiver.
%lname Last name of the user/receiver.
%dzone Destination zone.
%dnet Destination net.
%dnode Destination node.
%dpoint Destination point.
%daddress Destination Address.
%sysop Name of the Sysop (SysOp).
%fsysop Firstname of the Sysop.
%lsysop Last name of the Sysop.
%from Name of the message sender (MsgFrom).
%ffrom Firstname of the message sender.
%lfrom Last name of the message sender.
%board Boardname.
%zone The zone where the board is located.
%net The net number.
%node The node number.
%point The node point number.
%address Address of board
%date Current date.
%file Insert all the Filenames.
%size Insert the total file size in kilobytes.
%bsize Insert the total file size in bytes.
%hsize Insert half of the total file size in kilobytes.
%bhsize Insert half of the total file size in bytes.
%\ Insert soft <Cr> in the end of the line.
%subject Subject for the message (this option is not
available when forwarding messages using the
LotechMailer statement). (This meta-string must be
placed at position one in the first line in the
message textfile).
%repeat repeat line until file-count reached. (this meta-
string must be placed at position one in the
textline).
When using the %subject command you may wish to add all filenames
in the subject line.
%file Insert the filenames in the Subject line.
X_LIST 2.13 - PAGE 45
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
If you deal with Upload messages you may use the %repeat option,
this will generate a sequence of lines (with or without soft
<CR>) one entry for each of the files which the message concerns.
%repeat in messages.
%file Insert current file name.
%size Insert current file size in kilobytes.
%bsize Insert current file size in bytes.
%hsize Insert half of current file size in kilobytes.
%bhsize Insert half of current file size in bytes.
%fdate Insert the date from the current file.
%area Insert areas number.
X_LIST 2.13 - PAGE 46
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
WELCOME, THANX, DUPE & EXE-MSG FILE OLD FORMAT.
This old format is kept for downward compatibility, and will be
removed in a later version.
You can use the following meta-strings in the textfiles to be
sent as messages:
%1 Users first name.
%2 Filename(s) (uploaded files).
%3 Total size of the file(s) in kilobytes.
%4 Half of the total filesize(s) - Also in KB.
%5 Your name. This is taken from the 'MsgFrom' statement
explained above.
Sample textfile:
Hi %1!
I can see that you've uploaded %2 to the system. Sure hope
that other users will enjoy that %3 Kb of arc'ed stuff.
Cheers %5.
May result in:
Hi Viggo!
I can see that you've uploaded OEXE_110.ARC to the system.
Sure hope that other users will enjoy that 237 Kb of arc'ed
stuff.
Cheers Kristian Ottosen.
X_LIST 2.13 - PAGE 47
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
FORWARD MESSAGE FILE OLD FORMAT.
You can use the following meta-strings in the textfiles to be
sent as messages:
%1 Users first name.
%2 Filename (forwarded file).
%3 Total size of the file(s) in kilobytes.
%4 Date and Time.
%5 Your name. This is taken from the 'MsgFrom' statement
explained above.
Sample textfile:
Hi %1!
During my daily cleanup in the fileareas i found %2
floating around in my inbound area. Since I am short on
diskspace I would like you to save these %3 Kilo Bytes for
me.
Thanx - %4.
May result in:
Hi Mik!
During my daily cleanup in the fileareas i found Z2-DIFF.A06
floating around in my inbound area. Since I am short on
diskspace I would like you to save these 21 Kilo Bytes for
me.
Thanx - Per Holm.
X_LIST 2.13 - PAGE 48
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
OPUS LANGUAGE SUPPORT
If you are using OPUS ver 1.1x, you have an additional option of
language support in messages generated by X_LIST for the users
(Welcome, Thanx, Dupe, Exe and ExtMsg).
To enable this option three things need to be handled.
- You need a program to place the information in the OPUS.LOG
file, one such program is another utility from Bifrost
Unltd. named 'OpIntTop'. You need Ver 1.13... The logLine
must have the following format.
+ <Date> <Product> User language <language Number>
- You need to generate some extra text files for the User
messages (welcome, dupe, please arc messages). And name
these in a special way.. The first character in the
extension of the filename must be the language number (you
have the numbers 1..7 available). If you miss a file for a
secondary language (2..7), the primary language will be used
instead.
- You need to enable the language support for each message
function, this is done by adding a '#' as the first
character in the file extension.
"WelcomeMsg C:\XLST\Welcome.#xt"
"ThanxMsg C:\XLST\ThanxMsg.#xt"
X_LIST 2.13 - PAGE 49
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
PWD SECURITY FILE FOR FILE-FORWARD & DISTRIBUTION
Since there is almost no security on forwarded files i.e.
nodediff's FNEWS and many others in FidoNet we do have a security
problem..
The Security file is a textfile with the following format:
From: X_List@<Node>
To: X_List@<Node>
File: <FileName>
Password: <Password>
Size: <FileSize in bytes>
Subject: <Filecomment>
Origin: <Origin Node>
CRC: <CRC calculated checksum>
Area: <File Distribution Area>
Path: <Node1> <UnixDate> <Date String>
Path: <Node2> <UnixDate> <Date String>
Seen-By: <Seen by Node1>
Seen-By: <Seen by Node2>
The keywords should not be case sensitive.
From: The important field in the 'From:' statement is the
origin nodenumber, the senders name may be anything,
like the name of the product which made the .PWD file.
To: The important field in the 'To:' statement is the
destination nodenumber, the receivers name may be any
name you choose..
File: The name of the file sent, no path or wildcards are
allowed.
Password: The <Password> may contain up to 8 ASCII characters. If
no password has been specified, this field should be
left out of the .PWD file..
Size: The size of the file to be transmitted (used to check
if it is the correct file in the inbound directory of
the receiving system.
Subject: The Subject line contains a short description of the
file. This description may then be added to the
FILES.BBS for the area where the file has been placed.
Origin: Will contain the address of the originating system..
** Only in Area support **
CRC: When available this line will contain a CRC32 value for
the file distributed... The CRC information are not
used by X_List, but will be forwarded with both .PWD
and .TIC files... The CRC values must be generated by
CRC-32 (C) Barry Geller..
X_LIST 2.13 - PAGE 50
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
** Only in Area support **
Area: Used when supporting Routing of FileAreas...
** Only in Area support **
Path: Used to show the path a File went to get to your
system. Only used when the Area statement are active..
** Only in Area support **
Seen-By: List of nodes who saw this file along the path.
** Only in Area support **
Other lines might be added in the future..
The file will be placed in the OutBound area, the extension will
be xxxxxxxx.PWD, where xxxxxxxx will be a hex value of the number
of seconds that has past since Jan 1st, 1970.
The security files will be placed on hold right after the file it
describes... This is done to ensure the whole file was received..
The receiving system should have the possibility to check if one
or both the Password and the origin nodenumber are correct.
A sysop may get the same file from different sources, and would
like to have a password for the file, but all nodes should be
allowed to send the file to his system, as long as they use the
correct password..
Another Sysop may decide to use the origin address, and no
password for the file...
As soon as the files have been received on the destination
system, a program should check if the files are from valid
systems, and move these to the destination areas, (this should be
done to prevent the mailer from renaming the files in case of
dupes), and bad files should be moved to another area or
deleted.. X_List will check all files with extension .PW? to see
if it is a valid password file, and the files will be deleted
from the inbound area as soon as they have been read...
Here is some examples of Password files:
From: X_List@2:230/22
To: X_List@2:230/101
File: FNEWS706.ARC
Password: SECRET
Size: 4321
From: X_List@2:230/22
To: X_List@2:230/101
File: FNEWS707.ARC
Size: 6543
X_LIST 2.13 - PAGE 51
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
From: X_List@2:230/22
To: X_List@2:230/113
File: BOARDS11.ZIP
Password: HERMAN
Size: 38606
Subject: This is a test
Origin: 2:231/34
Area: TESTPER
Path: 2:231/34 653526857 Sun Sep 16 23:14:17 1990 GMT
Path: 2:230/22 665578787 3 Feb 91 10:59:47 GMT
Seen-By: 2:231/34
Seen-By: 2:230/22
Seen-By: 27:345/1
Seen-By: 2:230/113
From: X_List@2:230/22
To: X_List@27:345/1
File: BOARDS11.ZIP
Password: GERTRU
Size: 38606
Subject: This is a test
Origin: 2:231/34
Area: TESTPER
Path: 2:231/34 653526857 Sun Sep 16 23:14:17 1990 GMT
Path: 2:230/22 665578787 3 Feb 91 10:59:47 GMT
Path: 27:345/0 665578787 3 Feb 91 10:59:47 GMT
Seen-By: 2:231/34
Seen-By: 2:230/22
Seen-By: 27:345/0
Seen-By: 27:345/1
Seen-By: 2:230/113
X_LIST 2.13 - PAGE 52
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
TIC SECURITY FILE FOR FILE-ROUTING
TICK file distribution is widely used for the File Distribution
Networks within FidoNet, and X_List has been expanded to handle
.TIC files as well as it's own .PWD files.
A .TIC file must have the following format:
Area <Distribution Area>
File <FileName>
Desc <FileComment>
Origin <Origin Node>
From <Node that sent it to you>
CRC <Crc value (Not used by X_LIST)>
Update <not used by X_List>
Created <Software that created the .TIC file>
Path <Node1> <UnixDate> <Time String>
Seenby <Node1>
Seenby <Node2>
Pw <Password>
Here is a sample .TIC file..
Area TESTPER
File TESTFILE.ZIP
Desc Just a test
Origin 2:231/34
From 2:231/34
CRC 123456AC
Created by X_List Ver. 2.13 - (C) .....
Path 2:231/34 653526857 Sun Sep 16 23:14:17 1990 GMT
Seenby 2:231/34
Seenby 2:230/22
Pw TEST
The TICK file format has been developed by Barry Geller
More information about the TICK format may be found in the TICK
documentation..
Also you must keep in mind that X_LIST may not preserve
additional information in the .TIC files...
X_LIST 2.13 - PAGE 53
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
FILE DISTRIBUTION CONTROL FILE (XL_TICK.CTL)
The X_List file distribution controlfile are a subset of the
TICK.CFG control file for usage with the TICKET program.
Area: Distribution File Area Description. Used to
specify areas and nodes that are connected.
AREA <Directory or AreaNum> <AreaName>
<Node1> <Password> <Flags>
<Node2> <Password> <Flags>
<Flags> * : Accept Files.
& : Send Files.
P : Send as Pwd.
F : Send as Flea. (Future)
H : Send as HOLD.
C : Send as Crash.
M : Send follow-up message.(Future)
Sample:
AREA D:\tmp SPECIAL
2:231/34 HIPER *
2:230/31 HELLO *&H
27:27/0 HELLO *
AREA 21 EEGGNET
97:946/0 HIPER *
Hold: Directory to place the .TIC and .PWD files
generated when forwarding distribution files.
"Hold D:\Tmp\"
The following commands are accepted by the controlfile
interpreter, but currently not used by X_LIST:
IN, ZONE, NET, NODE, TZ, STOPDUP, TEMP, FLEA, FIDO, MAIL,
Logpath, Sent, QDIR, LineFmt, ListName, AKA, LOGSEEN, CRC,
LogCRC, Crc2Dup, NoWait.
X_LIST 2.13 - PAGE 54
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
INCLUDED X_LIST UTILITIES
MAKEXDIR
A small utility program is supplied with X_List. It is primarily
intended for use by people with a lot of files, but limited
diskspace.
It will make X_List list the size and date of the missing files
in the public list. Whenever a missing file is found in a
FILES.BBS file, X_List looks in a file named X_LIST.DIR and takes
the size and date of the missing file from this control-file and
puts in the public list. If the file missing is found in
X_LIST.DIR it will be flagged with an exclamation point (!)
between the filename and filesize.
FILE1.ARC ! 54728 24-12-88 This file was in X_LIST.DIR
FILE2.ARC missing This file was not in X_LIST.DIR
FILE3.ARC 32767 28-02-88 This file is online.
For more information read the MakeXDir.DOC file in the X_List
distribution archive...
Of cause it is pure non-sense to run MakeXDir for an area that
the users can't reach when they are online!
X_LIST 2.13 - PAGE 55
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
X_VANVAB
X_VanVab<Tm> uses the well known VanVab<Tm> technology to add a
little Avatar-color to the file listings generated by X_list
(both the Public and News-List).
** NOTE SYSTEM MUST BE ABLE TO HANDLE THE AVATAR EMULATION **
Usage : X_VanVab <Inputfilename> <Outputfilename>
Keep em' online!!
ADJUST
Small program to add or subtract to the users upload and download
counters..
For more information look at page 33. Or have peek into the
ADJUST.DOC file in the X_List distribution archive...
X_LIST 2.13 - PAGE 56
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
OTHER X_LIST UTILITIES
X_NEW
X_NEW (C) Bifrost Unlimited and Per Holm.
X_New is a small on-line X_LIST utility for the following BBS
systems OPUS 1.03, OPUS 1.1x and Maximus 1.02.
The purpose of X_NEW is to show the users a list of files arrived
since the last login (The user may optionally set another date to
be used)..
The information about the new files, are found in a filelist
generated by X_List...
X_NEW is distributed in an archive named X_NEW###.LZH where ###
are the three digits in the version number.
X_NEW101.LZH will contain X_NEW version 1.01..
OPINTTOP
OpintTop (C) Bifrost Unlimited and Per Holm.
OpintTop is a small on-line TOP-10 utility for OPUS CBCS (version
numbers below 1.10 is for OPUS 1.03, higher version numbers are
for OPUS 1.20).
OpintTop version 1.13 has a special feature for Opus 1.1x
language support, it may place a special line in the OPUS log
file with information about the language the user has choosed to
use..
OpintTop is distributed in an archive named OITOP###.LZH where
### are the three digits in the version number.
OITOP113.LZH will contain OpintTop ver. 1.13
X_LIST 2.13 - PAGE 57
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
HISTORY
Ver. 2.00
o Feel free to compare the documentation with the
documents from the elder versions.
Ver. 2.03
o Introduced the Licence statement to get some extra
facilities.
o Read system information from the Opus.Prm file.
o Matrix Mail supported for Forwarding and Daily reports.
o You may send a copy of the daily report to your
Co-SysOp.In the regular area or by MATRIX (might be
your point-net).
o You may want to send a matrix message along with the
files forwarded.
o You may customize the texts used in letters.
o X_LIST will now delete it's own messages when received.
This does not include messages written by earlier
X_LIST versions.
o Adding comments for new files adopted in the Files.Bbs.
o You may replace special characters in the public list
and FILES.BBS, useful for special characters like the
Danish.
o X_LIST will tidy your FILES.BBS in different ways etc.
by splitting descriptions that are too long to be
displayed by Opus<Tm> into separate lines with spaces
inserted to get the indent right.
o Customizing of the public list.
o Option to delete old copies of files.
X_LIST 2.13 - PAGE 58
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
Ver. 2.04
o Dropped the Licence statement stuff again.
o Files with extension .XMG will be forwarded as a Matrix
Message, containing the contents of the file (which
must be in text format).
o Touch facility (Set Date and Time on files).
o Mark newest files (Less than X days) with a star in the
file list.
o Make an extra filelist with only the new files.
o Delete empty (0 Byte) files from the file areas.
o Generate a weekly Master-Index file (For future use).
Ver. 2.05 - Never released
Ver. 2.06
o 'Level' now accepts values 0-32767 for QuickBBS
support.
o Added 'AreaFile' to read a QuickBBS area description
file.
o Improved the 'Forward' facility.
o X_List is not case-sensitive with filenames from the
Files.BBS files anymore.
o Fixed problem with change of year.
o Fixed problem in NewsList. The old version had some
problems deciding what was comments.
o Fixed some other minor problems.
Ver. 2.07-Gamma - Test release of ver 2.10 expired Oct 15, 1989
Ver. 2.08 to 2.09 - Skipped these versions.
Ver. 2.10
o The bug in the Dupe message function has been fixed.
o New Dupe criteria (more relaxed).
X_LIST 2.13 - PAGE 59
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
o Option to write messages depending on the file
extension to the uploaders.
o May now write a logfile of the X_List Session.
o Option to do some House Cleaning in the Outbound area.
o New CoSysOp statement.. The old ones has been removed..
o Almost no upper limit on number of 'Forward, Touch,
KeepLatest, Crap, FreeFile, Name, CoSysOp lines.
o Option to skip missing files from the Public List only.
o Make new version's of program available under magic
filenames (Ex. the nodelists, and diffs.).
o Touch is now able to handle wildcards.
o Crap is not case sensitive any more.
o Crap files will be deleted before the Public list is
generated for the current area.
o Able to generate .PKT files to be tossed into a message
database (for use with QuickBBS).
o Able to analyze QuickBBS log file
o Full Zone:Net/Node.Point support in matrix messages.
o Full Zone:Net/Node support in .HLO and Echo-mail (.PKT)
o Full Zone:Net/Node.Point support for CoSysOp Address.
o Full Zone:Net/Node.Point support on Forward statement.
o Added Support for FrontDoor OkFile "Mailer FD".
o MagicFix function for magic filenames (Binkley).
o Adjust fixed for QuickBBS files.BBS "BBS QuickBBS"
o You may now define your own CommaFile format.
o More user (SysOp) friendly message files.
o New ADJUST program able to handle either an OPUS or an
QuickBBS userfile. Made by Stig Jacobsen (2:231/16).
X_LIST 2.13 - PAGE 60
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
Ver. 2.11
o New address for the Postcards to Kristian Ottosen.
o Added support for random selected messages to the users
(Welcome, Thanx, Dupe, Exe, Ext and Forward messages).
o Added option to disable the Forward message to some
nodes (Using a /N in the NAME statement).
o Added Opus 1.10 Support.
o Added RemoteAccess support.
o Added support for moving files from one directory to
another.
o Added support for Secured file forwards.
o The 500 file limit in each area has been removed.
o Now finally available in an overlay version.
o Fixed the QuickBBS mode Bug from ver 2.10..
Ver. 2.11a - Maint update!
o Fixed bug with message bundles (.PKT files)
o Fixed errors in the .CTL sample files.
o Added some missing files to the distribution archive.
Ver. 2.12
o Added some support for Max 1.02.
o The name statement got a new flag '/L' (LotechMailer)
o Fixed area number in lists (now three digits).
o Fixed /F problem for the Move statement.
o Fixed bug with deleted files (wrong name was passed to
the log file).
o Fixed the bug in calculation of percentage of free
space on large harddisks. (uses code by Gerard de Haan
2:286/251)
o Trailing backslash on the path in the FLSearch file are
no longer necessary.
X_LIST 2.13 - PAGE 61
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
o Added support for Opus style log from RA.
o Far better log analysis, optionally mail session report
when using the OPUS or Binkley mailer. The report may
be placed in the DailyReport, or in separate file/msg.
o You may now add an alternative filename for the system
information file when using Maximus or RemoteAccess
o Added option to mail dupe & orphan reports in the Daily
Report area, and/or send a copy to the CoSysOp(s).
o Improved the CoSys statement with optional reports to
be sent in the morning (or whenever you're X_Listing).
o The NewsList will now show if F.REQ are possible for
the areas, just like the public list does...
o Added support to write direct into a RA/QuickBBS
message base...
Ver. 2.13
o RSPFiles support now in documentation, was already
implemented in version 2.12..
o New extension on temporary files '.$$$'
o Will now translate ALL lines when using the Convert
statement, not only the lines with filenames.
o Fixed several small problems in the BT Log analysis.
o Fixed bug with the Adjust file...
o You may now specify up to 11 Address lines (10 Aka's).
o Added Hold/Normal/Crash flag for forwarding of files.
o Removed limit of 10 Include areas..
o Fixed problem in Dupe and Orphan reports, could hang
the system.
o Fixed problem with last Max Area.
o Fixed Problem moving file in MSDOS 4.0x.
o Enabled wildcards in Crap statement.
o Improved usage of Show, Skip, Adopt, Reflow, Rewrite
and RemMiss statements, Single area support..
o Added FileMode statement for LAN support.
X_LIST 2.13 - PAGE 62
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
o Added TICK compatible file routing.
o Expanded the .PWD files to handle areas.
o Option to forward files received from .TIC to .PWD
files and the other way around...
X_LIST 2.13 - PAGE 63
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
NEW IDEAS FOR FEATURES THAT MIGHT SHOW UP LATER
o Handling of wildcards in FILES.BBS
o Option to create a list of files not arc'ed.
o Enhanced shirt ironing capabilities.
o Support for user flags in areas.
o Support for handling .FLE files to an area.
o Far better log reporting and message info.
o More QuickBBS support.
o More RemoteAccess Support.
o More Maximus CBCS support.
o Improved type checking on control file commands..
o Handle <TAB> in .CTL files.
o Generate list of Uploads.
o New and more powerful X_VanVab program.
X_LIST 2.13 - PAGE 64
X_LIST V 2.13 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
INDEX
.PWD Format 50 Lan-Wt 39 33
.TIC Format 53 Lan-Yg 39 WelcomeMsg 35
ADJUST 33, 56 Last 22 XListData 14
CONTENTS 2 Level 20 XLogFile 14
Control File License 13 ZapZero 26
Address 16 LogFile 30 Zone 16
Adopt 24 LogLevel 15 Zones 41
AdoptComment 27 LotechMailer CONTROLFILE
AreaFile 14 42 Area Maint. 24
BBS 15 Magic 29 Forward 34
BoardName 16 Mailer 16 General 13
CommaFile 18 MarkLast 22 Log Analysis 30
CommaFormat 19 MatrixPath Matrix 34
Convert 27 40 Message 34
CoSysOp 32 MaxAreas 22 Okfile 28
Crap 25 MaxDrive 17 Public List 18
DailyReport 30 MaxFiles 19 Distribution
Debug 17 Move 44 archive 8
Download 30 MsgArea 34 FILE-DISTRIBUTION
Drives 17 MsgDrArea 34 54
DupeMsg 37 MsgFrom 34 HISTORY 58
DupeReport 26 Name 43 INTL 40
EuroDate 22 Net 16 INTRODUCTION 10
ExeMsg 38 NewsList 18 Language support
ExtMsg 38 Node 17 22, 23, 35-39,
FileMode 15 OkFile 28 49, 57
First 22 OkHeader 28 LICENSE 6
Footer 20 OrphanReport MAKEXDIR 55
ForceIntl 40 26 MaxAreas 22
Forward 41 Outbound 40 Maximus
ForwardMsg 42 OutFile 18 Area handling 22
FreeFile 33 Password 28 MESSAGE
Header 20 Point 17 Dupe 47
Hindustan 17 PrmFile 13 Exe 47
HouseClean 40 QNewAll 33 File Format 45
InBound 35 ReFlow 25 Forward 48
Include 32 RemMiss 25 Thanx 47
Index 19 Rewrite 24 Welcome 47
KeepLatest 27 RSPFiles 35 Meta-string 45,
KillReceived 39 Secure 25 47, 48
Lan-Dr 39 SessionReport NetMail 39
Lan-Fa 22 31 OPINTTOP 57
Lan-Fl 23 Show 21 REQUIREMENTS 11
Lan-Fp 23 Skip 21 Utilities
Lan-Fr 23 SysOp 13 ADJUST 56
Lan-Mi 23 SystemPath MAKEXDIR 55
Lan-NF 23 13 OPINTTOP 57
Lan-Pa 39 ThanxMsg 35 X_NEW 57
Lan-Th 39 Tick 44 X_VANVAB 56
Lan-Ud 22 Touch 27 X_NEW 57
Lan-Ul 39 Upload 30 X_VANVAB 18, 56
Lan-We 39 UserAdjust
X_LIST 2.13 - PAGE i
